SD - Deepak - Mahesh - 2017-09 -04 - 61149 - Spec - Drop-Ship for Japan (Rizwan by 2017-10-30) #Delivery #Billing #Quality
PECIFICATIONS
61149-Spec- Drop-Ship for Japan
Purpose
Write a custom routine to meet the Japan drop-ship requirements.
Admin Info
Purpose
|
A routine to restrict the ZRDJ output for ZU3P orders if the plant is other than 9016.
|
Requested By
|
Rizwan Shah
|
Spec Created By
|
Deepak Yasam
|
Spec Created Date
|
09/04/2017
|
Spec QA by
|
Surya Basa
|
Objects
|
ZKOMKBV3
RV61B910
RVCOMFZZ
TFRM
TFRMT
V_T683_XX
|
Document Status
|
WIP
|
Estimates
Sl.No
|
Activity
|
Estimation in Hours
|
1
|
Research
|
00
|
2
|
Documentation
|
04
|
3
|
Development/ Config
|
16
|
4
|
Unit test in DEV
|
06
|
5
|
Unit test in QUA
|
00
|
6
|
Other activity
|
|
|
TOTAL
|
26
|
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]
None
Documents
[Attach any document(s) received for the requirement(s)]
None
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
Sl.
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
1
|
1. New output type should be created for 9016 plant and to TVARVC email
2. Remove 910 routine from ZRDJ and assign it to new output
3.ZRDJ should trigger for all the documents if condition record is maintained and to Customer email ID
|
Rizwan Shah
|
10/23/2017
|
NA
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
A routine to restrict the ZRDJ output for ZU3P orders if the plant is other than 9016
In Scope:
[List the activities to be included in scope]
Only the ZRDJ output is modified.
Out of Scope:
[Out of scope activities]
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
1. SO document type (AURAT) and plant (WERKS) should be added to the billing output header communication structure.
2. A new routine should be created with the logic to read the SO document type and plant ie., ZU3P and 9016.Then only the output should be triggered.
3. The RVCOMFZZ should be modified to fill the AURAT and WERKS from the corresponding tables so that the new routine can read them
3. ZRDJ output shouldn't be triggered for plant other than 9016 for ZU3P orders.
10/23/2017 -
1.
1. New output type should be created for 9016 plant and to TVARVC email
2. Remove 910 routine from ZRDJ and assign it to new output
3.ZRDJ should trigger for all the documents if condition record is maintained and to Customer email ID
Test Plan
[List test scenarios/cases to be executed here]
Test ID
|
Test Scenario
|
Expected result
|
SD-001
|
1.Create ZU3P SO with 9016 plant in 3200,10,00 sales area.
2.Create corresponding invoice.
|
The ZRDJ output should be triggered and the email should be sent to email ID maintained in TVARVC table
|
SD-002
|
1.Create ZU3P SO with 0620 plant in 3200,10,00 sales area.
2.Create corresponding invoice.
|
The ZRDJ output shouldn't be triggered.
|
SD-003
|
1.Create ZJRU SO with 9016 plant in 3200,10,00 sales area.
2.Create corresponding delivery and invoice.
|
The ZRDJ output should be triggered and the email should be sent to email ID maintained in TVARVC table
|
SD-004
|
1.Create ZJRU SO with 0620 plant in 3200,10,00 sales area.
2.Create corresponding delivery and invoice.
|
The ZRDJ output should be triggered and the email should be sent to email ID maintained in customer master.
|
Solution Details
[Provide complete technical details for configuration or programming here]
1. AURAT and WERKS are added in KOMKBV3 billing header output communication structure as below.
2. A new routine is created RV61B910 with the logic as below.
3. The RVCOMFZZ exit is coded to read AURAT and WERKS as below so that it can be filled in KOMKBV3 structure and there by to the new routine.
4. The new routine is added to ZRDJ output in the procedure by removing the existing 61 routine as below. The standard 61 routine logic is also added in 910 routine.

10/23/2017 -
1. New output type ZRDX is created with external send as medium and 0002 access sequence.
2. The RV61B910 routine should be changed to remove the document type (ZU3P) and only plant is maintained (9016).
3. The print program should be modified to add the ZRDX output and should trigger for TVARVC email ID but not for customer email ID.
4. The new output is assigned in the output procedure and 910 routine with new change is assigned. (Also, 910 routine is removed from ZRDJ and 62 is assigned )
Issues
[List Issues / Bugs identified in configuration or development]